Femto cell access point passthrough model

ABSTRACT

The subject innovation provides system(s) and method(s) to supply fixed, differentiated quality of service (QoS) for packetized traffic (e.g., voice and data) intended for femto cell coverage when transmitted concurrently with external broadband traffic. Quality of Service differentiation is supplied without an external implementation. Femto cell coverage is prioritized over concurrent packetized traffic to deliver a rich user experience for delay and jitter sensitive applications. A passthrough configuration for a femto access point (AP) facilitates supplying hard QoS for data packet streams, or flows, intended for femto cell coverage or non-femto-cell coverage. The femto AP receives a consolidated packet stream through backhaul link(s) and distinguishes flow(s) for femto coverage and flow(s) for auxiliary broadband coverage. The femto AP routes the flow(s) intended for femto with hard QoS according to QoS policy which can be determined by a network operator or a subscriber.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 61/052,055 filed on May 9, 2008, entitled “FEMTO CELL ACCESS POINTPASSTHROUGH MODEL.” The entirety of this provisional application isincorporated herein by reference.

TECHNICAL FIELD

The subject innovation relates to wireless communications and, moreparticularly, to prioritization of femto cell traffic relative todisparate concurrent broadband traffic in the absence of an externalquality of service implementation.

BACKGROUND

Femto cells—building-based wireless access points interfaced with awired broadband network—are generally deployed to improve indoorwireless coverage provided by a wireless network operator. Femto cellstypically operate in licensed portions of the electromagnetic spectrum,and generally offer plug-and-play installation; e.g., automaticconfiguration of femto access point. Improved indoor coverage includesstronger signal and improved reception (e.g., voice or sound), ease ofsession or call initiation and session or call retention as well.Coverage of a femto cell, or femto AP, is intended to be confined withinthe bounds of an indoor compound, in order to mitigate interferenceamong mobile stations covered by a macro cell and terminals covered bythe femto AP. Additionally, confined coverage can reduce cross-talkamong terminals serviced by disparate, neighboring femto cells as well.

Coverage improvements via femto cells can also mitigate customerattrition as long as a favorable subscriber perception regarding voicecoverage and other data services with substantive delay sensitivity isattained. User positive experience can require an external quality ofservice (QoS) implementation. While such QoS can supply networkresources to meet or exceed customer expectation in connection withvoice and data services, it can be costly and incompatible with legacyequipment(s) and service operators of femto and wired broadbandnetworks.

SUMMARY

The following presents a simplified summary of the innovation in orderto provide a basic understanding of some aspects thereof. This summaryis not an extensive overview of the innovation. It is intended toneither identify key or critical elements of the invention nor delineatethe scope of the innovation. Its sole purpose is to present someconcepts of the innovation in a simplified form as a prelude to the moredetailed description that is presented later.

The subject innovation provides system(s) and method(s) to supply fixed,differentiated quality of service (QoS) for packetized traffic (e.g.,voice and data) intended for femto cell coverage when transmittedconcurrently with external broadband traffic. Quality of Servicedifferentiation is supplied without an external implementation, andtakes place in the user plane. Femto cell coverage is prioritized overconcurrent packetized traffic to deliver a rich user experience fordelay and jitter sensitive applications. A passthrough configuration fora femto access point facilitates supplying hard QoS for data packetstreams, or flows, intended for femto cell coverage or non-femto-cellcoverage. To at least the latter end, the femto AP receives aconsolidated packet stream through backhaul link(s), and utilizes a flowmanagement component to distinguish flow(s) for femto coverage andflow(s) for auxiliary coverage. The flow management supplies, or routes,the flow(s) for devices, mobile or with wireless functionality, coveredby the femto cell with hard QoS according to various specifications,which can include operator policy, service agreement(s), promotionalcampaigns, coverage conditions (e.g., rural deployment, urbandeployment, deployment technology, number of subscribers to be coveredby the femto cell, applications to be exploited, and so forth). In anaspect, the various specifications can be retained in QoS profile(s). Inaddition, the flow management component delivers data packet flow(s) toa router that serves one or more devices, stationary or with wirelesscapability; the data packet flow(s) is delivered with hard QoS ofdisparate grade, or class, than QoS grade, or class, assigned to femtotraffic.

It is noted that aspects, features, or advantages of QoS differentiationeffected via a femto AP as described herein can be exploited withsubstantially any, or any, source of packet-based data or protocol(e.g., internet protocol (IP), asynchronous transfer mode (ATM), framerelay . . . ) for packetized data streams. In addition, QoSdifferentiation can be implemented for substantially any, or any, radiotechnology utilized by the femto AP that provides hard QoS for devicesserved through femto coverage.

The following description and the annexed drawings set forth in detailcertain illustrative embodiments of the subject innovation. Tofacilitate understanding, like reference numerals have been used, wherepossible, to designate like elements that are common to with thedrawings.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 a schematic deployment of a macro cell and a femto cell forwireless coverage in accordance with aspects described herein.

FIG. 2 is a block diagram of an example system that provides prioritizedhard QoS to data stream(s) directed to wireless device(s) served by afemto with respect to supplied hard QoS to external concurrent broadbandtraffic in accordance with aspects disclosed herein.

FIG. 3 illustrates a sketch of traffic in a femto cell with fixed QoS inaccordance with aspects disclosed herein.

FIG. 4 is a block diagram of an example embodiment of a flow managementcomponent in accordance with aspects described herein.

FIG. 5 is a block diagram of an example embodiment of a flow managementcomponent that facilitates configuration of a QoS policy in accordancewith aspects described herein.

FIG. 6 presents a flowchart of an example method for providingdifferentiated QoS for femto cell traffic in the presence of disparatebroadband traffic in accordance to aspects described in the subjectspecification.

FIG. 7 is an example method for delivering a data packet flow with a QoSbased at least in part on a QoS policy according to aspects describedherein.

FIG. 8 is an example method for configuring at least in part a QoSpolicy for differentiated prioritization of packetized data streamsdirected to femto coverage and packetized data streams directed tobroadband coverage.

FIG. 9 is a block diagram of an example femto access point that enablesand exploits various aspects disclosed in the subject specification.

FIG. 10 illustrates example macro and femto wireless networkenvironments that can exploit femto APs that utilize aspects of thesubject innovation.

DETAILED DESCRIPTION

The subject innovation is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject innovation. It may be evident, however,that the subject innovation may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectinnovation.

As used in this application, the terms “component,” “system,”“platform,” “interface” and the like are intended to refer to acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component may be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components mayreside within a process and/or thread of execution and a component maybe localized on one computer and/or distributed between two or morecomputers. Also, these components can execute from various computerreadable media having various data structures stored thereon. Thecomponents may communicate via local and/or remote processes such as inaccordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal).

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Furthermore, terms like “user equipment,” “mobile station,” “mobile,”“subscriber station,” “access terminal,” “terminal,” and similarterminology, refer to a wireless device utilized by a subscriber or userof a wireless communication service to receive or convey data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream. The foregoing terms are utilized interchangeably inthe subject specification and related drawings. Likewise, the terms“access point,” “base station,” “Node B,” “evolved Node B,” “Home AccessPoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or electronicappliance that serves and receives data, control, voice, video, sound,gaming, or substantially any data-stream or signaling-stream from a setof subscriber stations. Data and signaling streams can be packetized orframe-based flows. In addition, the terms “femto cell access point” and“femto access point” are utilized interchangeably.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth.

Referring to the drawings, FIG. 1 illustrates a wireless environmentthat includes macro cells and femto cells for wireless coverage inaccordance with aspects described herein. In wireless environment 100,two areas 105 represent “macro” cell coverage; each macro cell is servedby a base station 110. It should be appreciated that macro cells 105 areillustrated as hexagons; however, macro cells can adopt other geometriesgenerally dictated by the deployment or floor plan, geographic areas tobe covered (e.g., a metropolitan statistical area (MSA) or ruralstatistical area (RSA)), and so on. Macro coverage is generally intendedto serve mobile wireless devices, like UE 120 _(A), in outdoorslocations. An over-the-air wireless link 115 provides such coverage; thewireless link 115 comprises a downlink (DL) and an uplink (UL), andutilizes a predetermined band of the radio frequency (RF) spectrum. Asan example, UE 120 _(A) can be a Third Generation Partnership Project(3GPP) Universal Mobile Telecommunication System (UMTS) mobile phone. Itis noted that a base station, its associated electronics, circuitry orcomponents, and a wireless link operated in accordance to the basestation form a radio access network (RAN). In addition, base station 110communicates via backhaul link(s) 151 with a macro network platform 108,which in cellular wireless technologies (e.g., 3rd GenerationPartnership Project (3GPP) Universal Mobile Telecommunication System(UMTS), Global System for Mobile Communication (GSM)) represents a corenetwork. In an aspect, macro network platform 108 controls a set of basestations 110 that serve either respective cells or a number of sectorswithin such cells. Macro network platform 108 also communicates withother base stations (not shown) that serve other cells (not shown).Backhaul link(s) 151 can include a wired backbone link (e.g., opticalfiber backbone, twisted-pair line, T1/E1 phone line, a digitalsubscriber line (DSL) either synchronous or asynchronous, an asymmetricADSL, or a coaxial cable . . . ). Backhaul pipe(s) 155 link disparatebase stations 110.

In wireless environment 100, within one or more macro coverage cell 105,a set of femto cell 125 served by respective femto access points (APs)130 can be deployed. While in illustrative wireless environment 100three femto cells are deployed per macro cell, aspects of the subjectinnovation are geared to femto cell deployments with substantive femtoAP density, e.g., 10⁴-10⁸ femto APs 130 per base stations 110. A femtocell 125 typically covers an area that includes confined area 145, whichis determined, at least in part, by transmission power allocated tofemto AP 130, path loss, shadowing, and so forth. While coverage area125 and confined area 145 typically coincide, it should be appreciatedthat in certain deployment scenarios, coverage area 125 can include anoutdoor portion (e.g., a parking lot, a patio deck, a recreation areasuch as a swimming pool and nearby space) while area 145 spans anenclosed living space. Coverage area typically is spanned by a coverageradius that ranges from 20 to 100 meters. Confined coverage area 145 isgenerally associated with an indoor space such as a building, eitherresidential (e.g., a house, a condominium, an apartment complex) orbusiness (e.g., a library, a hospital, a retail store), which encompassa setting that can span about 5000 sq. ft.

A femto AP 130 typically serves a few (for example, 1-5) wirelessdevices (e.g., subscriber station 120B) within confined coverage area125 via a wireless link 135 which encompasses a downlink and an uplink.A femto network platform 109 can control such service, in addition tomobility handover from macro-to-femto handover and vice versa, andregistration and provisioning of femto APs. Control, or management, isfacilitated by backhaul link(s) 153 that connect deployed femto APs 130with femto network platform 109. Backhaul pipe(s) 153 are substantiallythe same as backhaul link(s) 151. In an aspect of the subjectinnovation, part of the control effected by femto AP 130 measurements ofradio link conditions and other performance metrics. Femto networkplatform 109 also includes components, e.g., nodes, gateways, andinterfaces, that facilitates packet-switched (PS) (e.g., internetprotocol (IP), ATM, frame relay . . . traffic and signaling generationfor networked telecommunication. It should be appreciated that femtonetwork platform 109 can be femto AP 130 can integrate seamlessly withsubstantially any packet switched (PS)-based and circuit switched(CS)-based network such as macro network platform 108. Thus, operationwith a wireless device such as 120 _(A) is substantially straightforwardand seamless when handover from femto-to-macro, or vice versa, takesplace. As an example, femto AP 130 can integrate into an existing 3GPPCore Network via conventional interfaces, or reference links, such asIu-CS, Iu-PS, Gi, or Gn.

It is to be noted that substantially all voice or data active sessionsassociated with subscribers within femto cell coverage (e.g., area 125)are terminated once the femto AP 130 is shut down; in case of datasessions, data can be recovered at least in part through a buffer (e.g.,a memory) associated with a femto gateway at the femto network platform.Coverage of a suspended or hotlined subscriber station or associatedaccount can be blocked over the air-interface. However, if a suspendedor hotlined customer who owns a femto AP 130 is in Hotline/Suspendstatus, there is no substantive impact to the customers covered throughthe subject femto AP 130. In another aspect, femto AP 130 can exploithigh-speed downlink packet access either via an interface with macronetwork platform 108 or through femto network platform 109 in order toaccomplish substantive bitrates.

In addition, in yet another aspect, femto AP 130 has a LAC (locationarea code) and RAC (routing area code) that is different from theunderlying macro network. These LAC and RAC are used to identifysubscriber station location for a variety of reasons, most notably todirect incoming voice and data traffic to appropriate pagingtransmitters, and emergency calls as well. As a subscriber station(e.g., UE 120 _(A)) that exploits macro coverage (e.g., cell 105) entersfemto coverage (e.g., area 125), the subscriber station (e.g., UE 120_(A)) attempts to attach to the femto AP 130 through transmission andreception of attachment signaling. The signaling is effected via DL/UL135; in an aspect of the subject innovation, the attachment signalingcan include a Location Area Update (LAU) and/or Routing Area Update(RAU). Attachment attempts are a part of procedures to ensure mobility,so voice calls and data sessions can continue even after amacro-to-femto transition or vice versa. It is to be noted that UE 120_(A) can be employed seamlessly after either of the foregoingtransitions. In addition, femto networks typically are designed to servestationary or slow-moving traffic with reduced signaling loads comparedto macro networks. A femto service provider network 165 (e.g., an entitythat commercializes, deploys, or utilizes femto access point 130) istherefore inclined to minimize unnecessary LAU/RAU signaling activity atsubstantially any opportunity to do so, and through substantially anyavailable means. It is to be noted that substantially any mitigation ofunnecessary attachment signaling/control is advantageous for femto celloperation. Conversely, if not successful, UE 120 _(A) is generallycommanded (through a variety of communication means) to select anotherLAC/RAC or enter “emergency calls only” mode. It is to be appreciatedthat this attempt and handling process can occupy significant UEbattery, and femto AP capacity and signaling resources (e.g.,communication of pilot sequences) as well.

When an attachment attempt is successful, UE 120 _(A) is allowed onfemto cell 125, and incoming voice and data traffic are paged and routedto the subscriber through the femto AP 130. To facilitate voice and datarouting, and control signaling as well, successful attachment can berecorded in a memory register, e.g., a Visited Location Register (VLR),or substantially any data structure stored in a network memory. It is tobe noted also that packet communication (e.g., voice and data traffic,and signaling) typically paged/routed through a backhaul broadband wirednetwork backbone 140 (e.g., optical fiber backbone, twisted-pair line,T1/E1 phone line, digital subscriber line (DSL) either synchronous orasynchronous, an asymmetric DSL, a coaxial cable . . . ). To this end,femto AP 130 is typically connected to the broadband backhaul networkbackbone 140 via a broadband modem (not shown). In an aspect of thesubject innovation, femto AP 130 can display status indicators forpower, active broadband/DSL connection, gateway connection, and genericor specific malfunction. In another aspect, no landline is necessary forfemto AP 130 operation.

It is to be noted that as a femto AP 130 generally relies on a backhaulnetwork backbone for routing and paging, and for packet communication,it can handle heterogeneous packetized traffic, or packetized datastreams, such as packet flows established for wireless devices served byfemto AP 130, and for devices served through the backhaul network pipe,broadband connection. It should be appreciated that to ensure a positivesubscriber experience, or perception, it is important for femto AP 130to maintain a high level of throughput for traffic (e.g., voice anddata) utilized on a mobile device for one or more subscribers while inthe presence of external, additional packetized, or broadband, trafficassociated with applications (web browsing, data transfer (e.g., contentupload), or the like) executed in devices within the femto coverage area(e.g., either area 125 or area 145). An example system that providesfixed QoS for femto cell traffic in the presence of disparate broadbandtraffic is discussed next.

FIG. 2 is a block diagram of an example system 200 that provides fixed,differentiated QoS for femto cell traffic (e.g., voice and data) anddisparate concurrent broadband traffic in accordance with aspectsdescribed herein. Quality of service (QoS) as provided by the aspects ofthe subject innovation does not rely on a QoS implementation external tothe femto cell (e.g., a QoS implementation provided through femtonetwork platform 190, or a broadband network that provides theconcurrent broadband traffic), which mitigates legacy issues withequipment and implementations since disparate packet protocol(s),multiplexing, modulation and coding rates are processed at the femto APregardless the source of data packet flow(s). Incompatibility amongoperators' interests as well. It is noted that, in an aspect of thesubject innovation, differentiated QoS takes place in the user plane.Example system 200 embodies a “femto access point passthroughconfiguration” in which broadband modem 210, or substantially any otherdevice that conveys data from a broadband backhaul backbone (e.g.,backhaul link(s) 153), conveys a packetized stream 215 over backhaulpipe segment 205 to femto AP 130, which discriminates the receivedstream into a first set of flows (e.g., data packet flow(s) 245 intendedfor a wireless device 255, or voice packet flow(s) 265 associated withsubscriber station 275) for femto coverage, and a second set of flowsassociated with background, or external to femto, concurrent broadbandtraffic (e.g., background packet flow(s) 285) intended for a router/hub295, or substantially any other connection or device, that deliverscoverage for personal computer (PC), a Wireless Fidelity (Wi-Fi) accesspoint, digital service(s) such as digital media frame, or the like.Packet flow(s) directed to femto coverage are delivered, and received,over wireless link 135, whereas background packet flow(s) 285 can bedelivered over a wired link 282. In an aspect of the subject innovation,femto cell coverage (e.g., data packet flow(s) 245 and voice packetflow(s) 265) is prioritized over concurrent packetized traffic in orderto deliver a rich user experience for delay and jitter sensitiveapplications such as realtime or streaming applications; for instance,both data packet flow(s) 245 and voice packet flow(s) 265 can receive aQoS Grade 1 with packet(s) prioritized over Grade 2 background packetflow(s) 285. It should be appreciated that most any, or any, QoScategorization such as Class of Service can be employed to distinguishamong QoS profiles for packet flow(s) directed to femto coverage orpacket flow(s) directed to background broadband coverage.

In an aspect, to facilitate flow discrimination and QoS provisionwithout reliance on external QoS implementation, femto AP 130 includes aflow management component 225. Quality of service provision can be basedat least in part on generalized traffic shaping, e.g., mechanism(s) toretain, preempt, cache, or dynamically reformat received packet dataflows. Supplied fixed QoS for packet flow(s) communicated to devicescovered by femto AP 130, and associated priority with respect tobackground packetized traffic, can be dictated in accordance at least inpart with various specifications that can comprise operator policy,service agreement(s), promotional campaigns, coverage conditions (e.g.,rural deployment, urban deployment, deployment technology, number ofsubscribers to be covered by the femto cell, applications to beexploited, available bandwidth . . . ) and so forth. In another aspect,such specification(s) can be stored in a memory component within flowmanagement 225 or functionally coupled thereto. Such specifications canembody a QoS policy. Substantially all communication (e.g.,transmission/reception of packet flows) is administered by communicationplatform 235, which generally comprises one or more components,including a processing unit (not shown) and a memory element (not shown)that facilitate wireless and wired communication. Next, a schematicrepresentation of traffic in the femto AP passthrough” configuration andassociated QoS, as well as aspects of system 200 are described ingreater detail.

FIG. 3 is a diagram 300 of an illustrative example “femto APpassthrough” traffic configuration in a femto cell with fixed QoS inaccordance with aspects disclosed herein. As discussed above, broadbandconnection 305 communicates traffic to a femto cell (e.g., femto AP 130)which supplies a first fixed QoS 310 for a portion of the receivedtraffic that is intended for femto coverage 325. Such portion of trafficis delivered wirelessly. In addition, a remaining portion of theconcurrent incoming traffic intended for devices served through backhaulpipe coverage, and delivered via broadband connection 305, can be can beconveyed to devices, stationary or mobile, that are served throughauxiliary non-femto coverage 335. In an aspect, the remaining portion ofthe concurrent traffic can be received by a broadband hub or router,which can include wired or wireless port(s), or other connector such asa Wi-Fi access point or a specific device (e.g., server, an IPtelevision set, a wireless digital media frame . . . ), associated withbroadband connection 305. As an illustration, provided QoS for femtocoverage 325 can be Grade 1 with packet priority over a Grade 2 QoS 320for auxiliary, or background, non-femto traffic 335. Herein, Grade 1 QoS310 is an improved quality of service over Grade 2 QoS 320.

FIG. 4 is a block diagram of an example embodiment 400 of a flowmanagement component in accordance with aspects described herein. Flowmanagement component 225 includes an identification component 410 thatdiscriminates between data packet flows directed to femto cell coverageand those directed to broadband coverage (e.g., data packets intendedfor a router, hub, non-femto access point, device(s), or the like).Identification component 410 provides discriminated packet traffic,e.g., femto and non-femto, to traffic shaping component 420 which canprocess data packet flows based at least in part on mechanism(s) toretain, preempt, cache (e.g., in traffic storage 446), or dynamicallyreformat received packet data flows, and thereby supply, or provide,data streams with fixed QoS. It should be appreciated that part of themechanism(s) can include evaluation of radio link condition(s) orwireless link 135, and evaluation of other available resources such asradio technologies, radio frequency carriers and so on. Traffic shapingcomponent 420 also can exploit at least in part a QoS policy stored inmemory element QoS policy(ies) 442 to determine one or more fixed QoSprofile, or realization, and supply the femto and non-femto data streamwith a determined QoS profile. A QoS policy can be defined by a networkoperator and received from a mobile network element (e.g., a femtogateway node) at the time of provisioning the femto AP that exploitsflow management component 225 for QoS differentiation as describedherein. In addition, a QoS policy can be received on an event-drivenbasis, wherein new QoS policies are received when broadband backhaulbackbone is upgraded (e.g., bandwidth increase as a result ofreplacement of T-carrier(s) with optical fiber, or upgrade of opticalfiber material(s) to a material with lower transmission losses . . . ),a new radio technology for femto communication is deployed, or a newfrequency carrier is include communication. A QoS policy can adoptdefault QoS profiles, or realization, with predetermined Grade ofService, or Class of Service, or specific guaranteed packet rates,packet loss rates, maximum packet error rates, maximum block error ratesor the like. In an aspect, different default profiles can be determinedfor various application or devices that consume one or more of the dataflows. It is noted that a QoS policy can be effected for all devicesauthorized to access femto service, as dictated by a configurable accesslist(s).

Packetized data flows intended for femto coverage and broadband coverage(e.g., non-femto) are conveyed to switch component 430 that routes femtopacketized flow(s) to wireless communication component(s), or wirelesscomponent(s) 452, within communication platform 235 for deliveryover-the-air to one or more intended wireless devices (e.g., wirelesscomputer 255, or UE 275), and non-femto packetized flow(s) to broadbandinterface 453 within communication platform 235 for delivery through abroadband link (e.g., link 282) to router/hub 295.

Processor 460 can be configured to confer, and can confer, at least inpart, the described functionality of flow management component 225 andcomponents therein, or can execute one or more of the component(s) inembodiment 400. To at least the foregoing ends, processor 460 canexecute code instructions or program modules stored in a memory (e.g.,memory 440) functionally coupled to flow management component 225, andexploit related data structures (e.g., objects, classes).

FIG. 5 is a block diagram of an example embodiment 500 of a flowmanagement component that facilitates configuration of a QoS policy inaccordance with aspects described herein. As described above, QoSpolicy(ies) 442 can be defined by a network operator and received from amobile network element at the time of provisioning a femto AP or anevent-driven basis; for instance, new QoS policies are received whenbroadband backhaul backbone is upgraded (e.g., bandwidth increase as aresult of replacement of T-carrier(s) with optical fiber, or upgrade ofoptical fiber material(s) to a material with lower transmission losses .. . ). In an aspect of the subject innovation, QoS policy also can beconfigured at least in part by a subscriber. Example embodiment 500,through at least configuration component 510, facilitatessubscriber-based configuration of a QoS policy. Configuration caninclude at least one of generation of a new QoS policy or modificationof an existing QoS policy. In an aspect, a QoS policy directive 505 canbe received by configuration component 510 as a part of composition ofQoS policy. Such a directive can enter a QoS requirement for at leastone of an application or a subscriber station. In addition, QoS policydirective 505 can remove extant QoS requirements from QoS policy(ies)442.

It is noted that a QoS policy requirement, or entry, is a criterion toset a specific QoS under predetermined circumstances, and a QoS profile,or realization, associated with the criterion. In an aspect, a QoSpolicy requirement can be received from a subscriber via a short messageservice (SMS) communication, an unstructured supplementary service data(USSD) message, or an email communication. Server(s) in a mobile networkcomponent can administer such communication(s) and deliver associatecontent(s). In another aspect, configuration component 510 can prompt,through signaling 512, a subscriber to enter a QoS policy directive whena new mobile device is authorized to exploit femto coverage, asreflected by changes to access list(s). Signaling 512 can be embodied ina SMS communication, a USSD message, or an email communication to amobile device of a subscriber associated with femto AP 130 andidentified as responsible for the account related to femto service.Alternatively, or additionally, signaling 512 can trigger visual oraural indicia in a display interface for femto AP. In yet anotheraspect, configuration component 510 can ensure normalization ofrequested QoS requirements within a QoS policy to ensure requested QoSprofiles, or realizations, can be supplied. Normalization herein refersto congruency among available communication resources and required QoSprofiles in a QoS requirement or QoS policy. Normalization can proceedthrough evaluation, e.g., via measurement(s) and estimate(s), ofavailable resources (e.g., capacity available within femto coveragearea, UL and DL radio quality, allocated radiating power . . . ) andestimation of required resources needed to meet requested QoS profiles.When a QoS policy fails to be normalized, e.g., include QoS requirementsthat cannot be fulfilled, at least one of the following is effected: anindication is delivered to a subscribed responsible for the accountassociated with the femto AP that operates in passthrough configurationor a default QoS, or a normalized default QoS is adopted.

Processor 520 can be configured to confer, and can confer, at least inpart, the described functionality of flow management component 225 andcomponents therein, or can execute one or more of the component(s) inembodiment 500. To at least the foregoing ends, processor 460 canexecute code instructions or program modules stored in a memory (e.g.,memory 440) functionally coupled to flow management component 225, andexploit related data structures (e.g., objects, classes).

In view of the example systems described above, example methodologiesthat can be implemented in accordance with the disclosed subject mattercan be better appreciated with reference to flowcharts in FIGS. 6-8. Forpurposes of simplicity of explanation, example methodologies disclosedherein are presented and described as a series of acts; however, it isto be understood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, a methodology disclosed herein could alternativelybe represented as a series of interrelated states or events, such as ina state diagram or call flow. Moreover, interaction diagram(s) mayrepresent methodologies in accordance with the disclosed subject matterwhen disparate entities enact disparate portions of the methodologies.Furthermore, not all illustrated acts may be required to implement amethodology in accordance with the subject specification. Further yet,two or more of the disclosed methodologies can be implemented incombination with each other, to accomplish one or more features oradvantages herein described. It should be still further appreciated thatthe methodologies disclosed hereinafter and throughout thisspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methodologies tocomputers for execution, and thus implementation, by a processor or forstorage in a memory.

FIG. 6 is a flowchart of an example method 600 for supplying fixed QoSfor flows served by a femto cell in the presence of disparate broadbandtraffic according to aspects described herein. In an aspect, it is to benoted that the subject example method 600 can be carried out by a femtocell access point within a passthrough configuration (see FIGS. 2 and3). In another aspect, performing example method 600 can benefit aspectsof QoS of a femto cell like mitigation of bottlenecks, or congestion, intraffic delivery for femto cell application(s) and subscriber. Withrespect to flowchart of example method 600, at act 610 a packet streamis received. The packet stream is a user-plane packetized data stream.In an aspect, such packet stream can be comprised by multiple flowsassociated with various applications executed in (i) wireless device(s)served by a femto cell and (ii) device(s), wired or with wirelesscapabilities, served through a broadband backhaul network. At act 620, afirst set of packet flows in the data stream is identified and a firstfixed QoS is provided, or assigned, to each flow in the set first set.It should be appreciated that the first set includes one or more packetflows. In another aspect, packet flows in the first set can be voice anddata packet flows intended for wireless device(s) served by a femtocell. It is noted that assigned first QoS can be same for each flow.Providing the first fixed QoS can include processing each flow in thefirst set of packet flows based at least in part on mechanism(s) toretain, preempt, cache, or dynamically reformat received packet dataflows. It should be appreciated that part of the mechanism(s) caninclude evaluation of radio link condition(s) or wireless link 135, orevaluation of other available resources such as capacity of a femtocoverage area, radio technologies, radio frequency carriers andassociated bandwidth, and so on. At act 630, a second set of flows inthe data stream is identified and a second QoS is provided, or assigned,to each flow in the second flow. It is noted that assigned second QoScan be same for each flow. In yet another aspect, traffic in the secondset of flows can correspond to non-femto broadband traffic intended fordisparate devices either wireless (e.g., a cordless phone, a wirelessmonitor) or wired (e.g., a television (TV) set such as an IPTV set, apersonal computer, a smart panel like a message board, and the like)served through a backhaul network pipe, or backbone. Providing thesecond fixed QoS can include processing each flow in the first set ofpacket flows based at least in part on mechanism(s) to retain, preempt,cache, or dynamically reformat received packet data flows. At act 640, apacket flow within at least one of the first set of packet flows or thesecond set of packet flows is conveyed according to a respectivelyprovided QoS (e.g., first QoS, or second QoS). In an aspect, as part ofpacket flow delivery, a component (e.g., switch component 430) routesthe packet flow to either a communication platform for wirelessdelivery, or a broadband interface for delivery through an auxiliarybroadband connection for non-femto coverage (see FIGS. 2-3).

A network operator can determine either the first QoS or the second QoS,or both, based at least in part on at least one of operator policy;service agreement(s), such as a business subscriber with substantivevoice and data consumption, or residential customer with modest voiceand data consumption; promotional campaigns which can supply premiumQoS, such as high guaranteed packet rate or guaranteed packet loss, forpredetermined time intervals or in exchange for selected product ofservice purchases; or coverage conditions (e.g., rural deployment, urbandeployment, deployment radio technology, number of subscribers to becovered by a femto cell, applications to be exploited, and so forth).Determination of first QoS and second QoS establish relative priority ofdata flow delivery. It should be appreciated that substantially any QoScategorization such as Grade of Service, Class of Service, guaranteedbitrate, guaranteed packet rate, maximum packet loss rate, maximum blockerror rate, etc. can be utilized to assign the first and second QoS andthus their respective prioritization.

FIG. 7 is an example method 700 for delivering a data packet flow with aQoS based at least in part on a QoS policy according to aspectsdescribed herein. A femto AP or one or more components therein (e.g., aflow management component 225) can effect the subject example method. Inan aspect, a processor that confers, at least in part, the functionalityof the one more components also can enact this example method 700. Atact 710, a QoS policy is configured for at least one of packetizedtraffic intended to be served through femto coverage or packetized flowtraffic intended to be served through auxiliary non-femto coverage. Inan aspect, auxiliary non-femto coverage is provided through connectionto a broadband traffic router (e.g., external to the femto AP thatimplements the subject example method. At act 720, a first packet flowintended for a device, either mobile or with wireless capability, servedthrough femto coverage from a second packet flow intended for a deviceserved through the femto coverage is discriminated from a second packetflow intended for a device, wired or with wireless capability, servedthrough the auxiliary non-femto coverage. At act 730, a fixed QoS issupplied to the first packet flow in accordance with the configured QoSpolicy. At act 740, the first packet flow is delivered with the suppliedQoS. Delivery of the first packet flow with the supplied QoS includesrouting the first packet flow to communication platform (e.g.,communication platform 235).

FIG. 8 is an example method 800 for configuring at least in part a QoSpolicy for differentiated prioritization of packetized data streamsdirected to femto coverage and packetized data streams directed tobroadband coverage. A femto AP or one or more components therein (e.g.,configuration component 510) can effect the subject example method. Inan aspect, a processor that confers, at least in part, the functionalityof the one more components also can enact this example method 800. Atact 810 a QoS policy is received for at least one of packetized trafficintended to be served through femto coverage or packetized trafficintended to be served through auxiliary non-femto coverage. In anaspect, the QoS policy can be defined by a network operator and receivedfrom a mobile network element (e.g., a femto gateway node) at the timeof provisioning the femto AP that enacts the subject example method 800.In addition, a QoS policy can be received on an event-driven basis,wherein new QoS policies are received when broadband backhaul backboneis upgraded (e.g., bandwidth increase as a result of replacement ofT-carrier(s) with optical fiber, or upgrade of optical fiber material(s)to a material with lower transmission losses . . . ). At act 820, a QoSpolicy directive is received for at least one of the packetized trafficintended to be served through femto coverage or the packetized trafficintended to be served through auxiliary non-femto coverage. In anaspect, a QoS policy directive can enter a QoS requirement for at leastone of an application or a subscriber station. In addition, a QoS policydirective can remove extant QoS requirements from stored QoS policy(ies)442. At act 830, at least one of the received QoS policy or a QoS policyassociated with the received QoS policy directive is retained. Retaininga QoS policy associated with the QoS policy directive can include addinga QoS requirement to an existing QoS policy as a result of effecting thereceived QoS directive; for instance, when a new data applicationbecomes available to be served through femto coverage, a specific QoScan be configured for such application. In addition, retaining at leastone of the received QoS policy or a QoS policy associated with thereceived QoS policy directive can include validating the QoS policy tobe retained is normalized, where normalization has been describedhereinbefore.

To provide further context for various aspects of the subjectspecification, FIG. 9 and FIG. 10 illustrate, respectively, a blockdiagram of an example embodiment of a femto cell access point that canenable and exploit features or aspects of the subject innovation andexample macro and femto wireless network environments that can exploitfemto APs that utilize aspects of the subject innovation in accordancewith various aspects of the subject specification. In embodiment 900,femto AP 905 can receive and transmit signal(s) (e.g., attachmentsignaling) from and to wireless devices like femto access points, accessterminals, wireless ports and routers, or the like, through a set ofantennas 920 ₁-920 _(N) (N is a positive integer). It should beappreciated that antennas 920 ₁-920 _(N) embody at least in partwireless component(s) 452, and are a part of communication platform 915,which comprises electronic components and associated circuitry thatprovides for processing and manipulation of received signal(s) andsignal(s) to be transmitted. Such electronic components and circuitryembody at least in part wireless component(s) 452; communicationplatform 915 operates in substantially the same manner as communicationplatform 235 described hereinbefore. In an aspect, communicationplatform 915 includes a receiver/transmitter 916 that can convert signalfrom analog to digital upon reception, and from digital to analog upontransmission. In addition, receiver/transmitter 916 can divide a singledata stream into multiple, parallel data streams, or perform thereciprocal operation. Coupled to receiver/transmitter 916 is amultiplexer/demultiplexer 917 that facilitates manipulation of signal intime and frequency space. Electronic component 917 can multiplexinformation (data/traffic and control/signaling) according to variousmultiplexing schemes such as time division multiplexing (TDM), frequencydivision multiplexing (FDM), orthogonal frequency division multiplexing(OFDM), code division multiplexing (CDM), space division multiplexing(SDM). In addition, mux/demux component 917 can scramble and spreadinformation (e.g., codes) according to substantially any code known inthe art; e.g., Hadamard-Walsh codes, Baker codes, Kasami codes,polyphase codes, and so on. A modulator/demodulator 918 is also a partof communication platform 915, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like. Communicationplatform 915 also includes a coder/decoder (codec) component 919 thatfacilitates decoding received signal(s), and coding signal(s) to convey.

Femto access point 905 also includes a processor 935 configured toconfer functionality, at least in part, to substantially any electroniccomponent in femto AP 905. In particular, processor 935 can facilitatepacketized flow management (e.g., identification and provision of fixedQoS) associated with flow management component 910, which operates inthe same manner as flow management component 910 in accordance tovarious aspects and embodiments disclosed herein.

Additionally, femto AP 905 includes display interface 912, which candisplay functions that control functionality of femto AP 905, or revealoperation conditions thereof. In addition, display interface 912 caninclude a screen to convey information to an end user; for instance,display interface 912 can display a message to restart femto AP 905, orenter a QoS directive. In an aspect, display interface 912 can be aliquid crystal display (LCD), a plasma panel, a monolithic thin-filmbased electrochromic display, and so on. Moreover, display interface canalso include a component (e.g., speaker(s)) that facilitatescommunication of aural indicia, which can also be employed in connectionwith messages that convey operational instructions to an end user.Display interface 912 also facilitates data entry (e.g., through alinked keypad or via touch gestures), which can facilitated femto AP 905to receive external commands (e.g., restart operation).

Broadband interface facilitates connection of femto AP 905 to abroadband network link such as backhaul links 205 and 282 (not shown),which enable incoming and outgoing data flow, respectively. Broadbandnetwork interface 914 can be internal or external to femto AP 905, andit can utilize display interface 912 for end-user interaction and statusinformation delivery.

Processor 935 also is functionally connected to communication platform915 and can facilitate operations on data (e.g., symbols, bits, orchips) for multiplexing/demultiplexing, such as effecting direct andinverse fast Fourier transforms, selection of modulation rates,selection of data packet formats, inter-packet times, etc. Moreover,processor 935 is functionally connected to display interface 912 andbroadband interface 914 to confer, at least in part functionality toeach of such components.

In femto AP 905, memory 945 can store data structures, code instructionsand program modules, system or device information, code sequences forscrambling, spreading and pilot transmission, femto AP floor planconfiguration, and so on. Processor 935 is coupled to the memory 945 inorder to store and retrieve information necessary to operate and/orconfer functionality to communication platform 915, flow managementcomponent 910, and other components of femto access point 905.

With respect to FIG. 10, wireless communication environment 1000includes two wireless network platforms: (i) A macro network platform1010 which serves, or facilitates communication with user equipment 1075(e.g., mobile 120 _(A)) via a macro radio access network (RAN) 1070. Itshould be appreciated that in cellular wireless technologies (e.g., 3GPPUMTS, HSPA, 3GPP LTE, 3GPP2 UMB), macro network platform 1010 isembodied in a Core Network. (ii) A femto network platform 1080, whichcan provide communication with UE 1075 through a femto RAN 1090, whichis linked to the femto network platform 1080 via backhaul pipe(s) 1085(e.g., backhaul link(s) 153). It should be appreciated that macronetwork platform 1010 typically hands off UE 1075 to femto networkplatform 1080 once UE 1075 attaches (e.g., through macro-to-femtohandover) to femto RAN 1090, which includes a set of deployed femto APs(e.g., femto AP 130) that can operate in accordance with aspectsdescribed herein.

It is noted that RAN includes base station(s), or access point(s), andits associated electronic circuitry and deployment site(s), in additionto a wireless radio link operated in accordance with the basestation(s). Accordingly, macro RAN 1070 can comprise various coveragecells like cell 105, while femto RAN 1090 can comprise multiple femtocell access points such as femto AP 130. Deployment density in femto RAN1090 is substantially higher than in macro RAN 1070.

Generally, both macro and femto network platforms 1010 and 1080 includecomponents, e.g., nodes, gateways, interfaces, servers, or platforms,that facilitate both packet-switched (PS) (e.g., internet protocol (IP),frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS)traffic (e.g., voice and data) and control generation for networkedwireless communication. In an aspect of the subject innovation, macronetwork platform 1010 includes CS gateway node(s) 1012 which caninterface CS traffic received from legacy networks like telephonynetwork(s) 1040 (e.g., public switched telephone network (PSTN), orpublic land mobile network (PLMN)) or a SS7 network 1060. Circuitswitched gateway 1012 can authorize and authenticate traffic (e.g.,voice) arising from such networks. Additionally, CS gateway 1012 canaccess mobility, or roaming, data generated through SS7 network 1060;for instance, mobility data stored in a VLR, which can reside in memory1030. Moreover, CS gateway node(s) 1012 interfaces CS-based traffic andsignaling and gateway node(s) 1018. As an example, in a 3GPP UMTSnetwork, PS gateway node(s) 1018 can be embodied in gateway GPRS supportnode(s) (GGSN).

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 1018 can authorize and authenticatePS-based data sessions with served (e.g., through macro RAN) wirelessdevices. Data sessions can include traffic exchange with networksexternal to the macro network platform 1010, like wide area network(s)(WANs) 1050, enterprise networks (NW(s)) 1070 (e.g., enhanced 911), orservice NW(s) 1080 like IP multimedia subsystem (IMS); it should beappreciated that local area network(s) (LANs), which may be a part ofenterprise NW(s), can also be interfaced with macro network platform1010 through PS gateway node(s) 1018. Packet-switched gateway node(s)1018 generates packet data contexts when a data session is established.To that end, in an aspect, PS gateway node(s) 1018 can include a tunnelinterface (e.g., tunnel termination gateway (TTG) in 3GPP UMTSnetwork(s); not shown) which can facilitate packetized communicationwith disparate wireless network(s), such as Wi-Fi networks. It should befurther appreciated that the packetized communication can includemultiple flows that can be generated through server(s) 1014. It is to benoted that in 3GPP UMTS network(s), gateway node(s) 1018 (e.g., GGSN)and tunnel interface (e.g., TTG) comprise a packet data gateway (PDG).

Macro network platform 1010 also includes serving node(s) 1016 thatconvey the various packetized flows of information, or data streams,received through PS gateway node(s) 1018. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 1014 in macro network platform 1010 canexecute numerous applications (e.g., location services, online gaming,wireless banking, wireless device management . . . ) that generatemultiple disparate packetized data streams or flows, and manage (e.g.,schedule, queue, format . . . ) such flows. Such application(s), forexample can include add-on features to standard services provided bymacro network platform 1010. Data streams can be conveyed to PS gatewaynode(s) 1018 for authorization/authentication and initiation of a datasession, and to serving node(s) 1016 for communication thereafter.Server(s) 1014 can also effect security (e.g., implement one or morefirewalls) of macro network platform 1010 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 1012 and PS gateway node(s) 1018 canenact. Moreover, server(s) 1014 can effect time protocols (e.g., NetworkTime Protocol) and embody one or more portions of clock strata.Furthermore, server(s) 1014 can provision services from externalnetwork(s), e.g., WAN 1050, or Global Positioning System (GPS)network(s), which can be a part of enterprise NW(s) 1080. It is to benoted that server(s) 1014 can include one or more processor configuredto confer at least in part the functionality of macro network platform1010. To that end, the one or more processor can execute codeinstructions stored in memory 1030, for example.

In example wireless environment 1000, memory 1030 stores informationrelated to operation of macro network platform 1010. Information caninclude business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 1030 can also store information fromat least one of telephony network(s) 1040, WAN 1050, SS7 network 1060,enterprise NW(s) 1070, or service NW(s) 1080.

Regarding femto network platform 1080, it includes a femto gatewaynode(s) 1084, which have substantially the same functionality as PSgateway node(s) 1018. Additionally, femto network platform 1080 includefemto serving node(s) 1020 which have substantially the samefunctionality as serving node(s) 1016. Disparate gateway node(s) 1084can control or operate disparate sets of deployed femto APs, which canbe a part of femto RAN 1090. In an aspect, as described herein, one ormore of the femto APs in the set of deployed femto APs can be configuredin a passthrough configuration, conveying data streams via respectivewired broadband link 1086 to respective hubs or routers 1087 thatsupplies the data streams to one or more devices; the one or more femtoAPs that supply data streams also receive data streams from respectivehubs or routers 1087. In an aspect of the subject innovation, femtogateway node(s) 1084 can aggregate operational data received fromdeployed femto APs. Moreover, femto gateway node(s) 1084, can conveyreceived attachment signaling to attachment component 1020. It should beappreciated that while attachment component is illustrated as externalto gateway node(s) 1084, attachment component 1020 can be an integralpart of gateway node(s) 1084.

Memory 1086 can retain additional information relevant to operation ofthe various components of femto network platform 1080. For exampleoperational information that can be stored in memory 1086 can comprise,but is not limited to, subscriber intelligence; contracted services;maintenance and service records; femto cell configuration (e.g., devicesserved through femto RAN 1090; authorized subscribers associated withone or more deployed femto APs); service policies and specifications;privacy policies; add-on features; so forth.

Server(s) 1082 have substantially the same functionality as described inconnection with server(s) 1014. In an aspect, server(s) 1082 can executemultiple application(s) that provide service (e.g., voice and data) towireless devices served through femto RAN 1090. Server(s) 1082 can alsoprovide security features to femto network platform. In addition,server(s) 1082 can manage (e.g., schedule, queue, format . . . )substantially all packetized flows (e.g., IP-based, frame relay-based,ATM-based, X.25-based . . . ) it generates in addition to data receivedfrom macro network platform 1010. Furthermore, server(s) 1082 can effectprovisioning of femto cell service, and effect operations andmaintenance. It is to be noted that server(s) 1082 can include one ormore processors configured to provide at least in part the functionalityof femto network platform 1080. To that end, the one or more processorscan execute code instructions stored in memory 1086, for example.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, the term “memory” refers to data stores,algorithm stores, and substantially any other information store relevantto operation and functionality of a component comprising the memory; forinstance, such information can comprise, but is not limited tocomprising, subscriber information, femto cell configuration (e.g.,devices served by a femto AP) and service policies and specifications,location identifiers, and so forth. It will be appreciated that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory.By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

Various aspects or features described herein may be implemented as amethod; apparatus, either as hardware or hardware and software orfirmware; or article of manufacture using standard programming and/orengineering techniques. Implementation(s) that include software orfirmware can be implemented at least in part through program modulesstored in a memory and executed by a processor. The term “article ofmanufacture” as used herein is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media. Forexample, computer readable media can include but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips. . . ), optical discs [e.g., compact disk (CD), digital versatile disc(DVD), Blu-ray disc (BD) . . . ], smart cards, and flash memory devices(e.g., card, stick, key drive . . . ).

What has been described above includes examples of the claimed subjectmatter. It is, of course, not possible to describe every conceivablecombination of components or methodologies for purposes of describingthe claimed subject matter, but one of ordinary skill in the art mayrecognize that many further combinations and permutations of the claimedsubject matter are possible. Accordingly, the claimed subject matter isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in either the detailed description orthe claims, such term is intended to be inclusive in a manner similar tothe term “comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

1. A femto access point, comprising: a communication platform configuredto receive a packetized stream in a user plane across a broadbandnetwork; an identification component configured to discriminate thepacketized stream into a first packet flow for a first device servedwithin femto cell coverage and a second packet flow for a second deviceserved within non-femto-cell background coverage; and a traffic shapingcomponent configured to provide a first fixed quality of service for thefirst packet flow in accordance with a first quality of service policyfor wireless transmission by the femto access point and a second fixedquality of service for the second packet flow in accordance with asecond quality of service policy for transmission across the broadbandnetwork.
 2. The femto access point of claim 1, wherein the first qualityof service policy is different from the second quality of servicepolicy.
 3. The femto access point of claim 1, wherein the first qualityof service policy is based on an evaluation of available resources. 4.The femto access point of claim 1, wherein the first quality of servicepolicy is defined by at least a subscriber.
 5. The femto access point ofclaim 4, further comprising a configuration component configured toreceive a modification to the first quality of service policy from thesubscriber.
 6. The femto access point of claim 5, wherein themodification removes existing quality of service requirements.
 7. Thefemto access point of claim 1, further comprising a switch componentthat routes the first packet flow for the first device served by femtocell coverage to a wireless communication component for deliveryover-the-air to a wireless device.
 8. The femto access point of claim 7,wherein the switch component is configured to route the second packetflow for the second device served within the non-femto-cell backgroundcoverage to a broadband interface for delivery through a wired broadbandlink to a first component configured to supply the non-femto-cellbackground coverage.
 9. The femto access point of claim 8, furthercomprising a second component configured to convey the first packet flowfor the first device served within the femto cell coverage and thesecond packet flow for the second device served within thenon-femto-cell background coverage.
 10. The femto access point of claim1, wherein the first quality of service policy is defined by a networkoperator.
 11. A method, comprising: receiving a packet stream at a femtoaccess point; identifying a first packet in the packet stream utilizedfor femto cell coverage and a second packet in the packet streamutilized for wired broadband coverage at the femto access point;providing a first quality of service grade to the first packet accordingto a quality of service policy and a second quality of service grade tothe second packet according to the quality of service policy at thefemto access point; wirelessly conveying the first packet according tothe first quality of service grade from the femto access point to awireless device; and non-wirelessly conveying the second packetaccording to the second quality of service grade from the femto accesspoint to a broadband hub.
 12. The method of claim 11, wherein theproviding comprises providing the first quality of service grade to thefirst packet and the second quality of service grade to the secondpacket, wherein the first quality of service grade is of a higherpriority than the second quality of service grade.
 13. The method ofclaim 11, wherein the providing further comprises providing the firstquality of service grade to the first packet and the second quality ofservice grade to the second packet based on evaluating availableresources.
 14. The method of claim 11, further comprising processing thefirst packet and the second packet based on an available wireless linksecond.
 15. The method of claim 11, further comprising configuring thequality of service policy based on a quality of service policydirective.
 16. The method of claim 11, further comprising configuringthe quality of service policy based on an input from a user.
 17. Themethod of claim 11, further comprising processing the first packet andthe second packet based on a policy for retaining the first packet. 18.The method of claim 11, further comprising configuring the quality ofservice policy based on a quality of service requirement for anapplication.
 19. The method of claim 11, further comprising configuringthe quality of service policy by adding a quality of service requirementto the quality of service policy.
 20. The method of claim 11, furthercomprising validating the quality of service policy.
 21. Anon-transitory computer-readable storage medium having instructionsstored thereon that, in response to execution by a computing device,cause the computing device to perform operations comprising: receiving adata packet stream across a broadband connection at a femto cell;processing the data packet stream at the femto cell and identifying afirst packet flow directed to femto cell coverage and a second packetflow dedicated to broadband coverage; providing a first quality ofservice profile to the first packet flow based on a quality of servicepolicy at the femto cell; providing a second quality of service profileto the second packet flow based on the quality of service policyapplying to the femto cell; wirelessly conveying the first packet flowaccording to the first quality of service policy; and conveying thesecond packet flow according to the second quality of service policyacross the broadband connection.
 22. The computer-readable storagemedium of claim 21, the operations further comprising: configuring thequality of service policy based on an input from a subscriber.
 23. Anapparatus comprising: a memory that stores components, comprising: anidentification component configured to analyze a packet stream receivedacross a broadband connection and to discriminate between a first datapacket flow directed to femto cell coverage and a second data packetflow directed to broadband coverage in a packet stream; a trafficshaping component configured to process the first data packet flowaccording to a first quality of service according to a quality ofservice policy and the second data packet flow according to a secondquality of service according to the quality of service policy; and aswitch component configured to route the first data packet flow to awireless component that transmits the first data packet flow wirelesslyaccording to the first quality of service and to route the second datapacket flow to a wired component that transmits the second data packetflow across the broadband connection according to the second quality ofservice.